Method, device, and system for securely sharing media content from a source device

ABSTRACT

A method, device, and system for sharing media content with a sink device includes performing a cryptographic key exchange with the sink device and generating an authorization key in a security engine of a system-on-a-chip (SOC) of a source device. The method may also include generating an exchange key as a function of the authorization key and a packet key as a function of the exchange key. Such key generation occurs in the security engine of the SOC, and the keys are stored in a secure memory of the security engine.

BACKGROUND

The generation, sharing, and consumption of digital media content continue to grow as consumer devices capable of interacting with such content become ubiquitous. The desire to share digital media content between consumer devices, especially in the home environment, is increasing in unison with the increased exposure to digital media content. To ensure that two media devices can properly share digital media content while also ensuring the digital rights of such content remain protected, digital media content delivery protocols have been developed by various authority organizations. One such organization is the Digital Living Network Alliance (DLNA), which has established various interoperability protocols and standards for sharing media content between media devices. For example the Digital Transmission Content Protection (DTCP) protocol is a security protocol that defines security guidelines and compliance requirements for securely sharing media content between media devices. Digital Transmission Content Protection over Internet Protocol (DTCP-IP) is a sub-set protocol of the DTCP protocol directed to sharing media content between media devices over a network.

Some media devices utilize system-on-a-chip (SOC) designs due to their relatively small footprint. SOC devices are integrated circuits that incorporate various components, in addition to the processing core, of electronic systems on a single die. For example, an SOC may include a processor core, memory controller, video components, audio components, and/or communication components on a single chip.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention described herein is illustrated by way of example and not by way of limitation in the accompanying figures. For simplicity and clarity of illustration, elements illustrated in the figures are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference labels have been repeated among the figures to indicate corresponding or analogous elements.

FIG. 1 is a simplified block diagram of at least one embodiment of a system for sharing media content from a media source device having a system-on-a-chip (SOC) to a media sink device;

FIG. 2 is a simplified flow diagram of at least one embodiment of a method for provisioning a security engine of the SOC of the media source device;

FIG. 3 is a simplified flow diagram of at least one embodiment of a method for authenticating the media sink device of FIG. 1; and

FIG. 4 is a simplified flow diagram of at least one embodiment of a method for securely sharing media content with the media sink device of FIG. 1.

DETAILED DESCRIPTION OF THE DRAWINGS

While the concepts of the present disclosure are susceptible to various modifications and alternative forms, specific exemplary embodiments thereof have been shown by way of example in the drawings and will herein be described in detail. It should be understood, however, that there is no intent to limit the concepts of the present disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives consistent with the present disclosure and the appended claims.

In the following description, numerous specific details such as logic implementations, opcodes, means to specify operands, resource partitioning/sharing/duplication implementations, types and interrelationships of system components, and logic partitioning/integration choices are set forth in order to provide a more thorough understanding of the present disclosure. It will be appreciated, however, by one skilled in the art that embodiments of the disclosure may be practiced without such specific details. In other instances, control structures, gate level circuits and full software instruction sequences have not been shown in detail in order not to obscure the invention. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

Embodiments of the invention may be implemented in hardware, firmware, software, or any combination thereof. Embodiments of the invention implemented in a computer system may include one or more bus-based interconnects or links between components and/or one or more point-to-point interconnects between components. Embodiments of the invention may also be implemented as instructions carried by or stored on a machine-readable medium, which may be read and executed by one or more processors. A machine-readable medium may be embodied as any device, mechanism, or physical structure for storing or transmitting information in a form readable by a machine (e.g., a computing device). For example, a machine-readable medium may be embodied as read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; mini- or micro-SD cards, memory sticks, electrical signals, and others.

In the drawings, specific arrangements or orderings of schematic elements, such as those representing devices, modules, instruction blocks and data elements, may be shown for ease of description. However, it should be understood by those skilled in the art that the specific ordering or arrangement of the schematic elements in the drawings is not meant to imply that a particular order or sequence of processing, or separation of processes, is required. Further, the inclusion of a schematic element in a drawing is not meant to imply that such element is required in all embodiments or that the features represented by such element may not be included in or combined with other elements in some embodiments.

In general, schematic elements used to represent instruction blocks may be implemented using any suitable form of machine-readable instruction, such as software or firmware applications, programs, functions, modules, routines, processes, procedures, plug-ins, applets, widgets, code fragments and/or others, and that each such instruction may be implemented using any suitable programming language, library, application programming interface (API), and/or other software development tools. For example, some embodiments may be implemented using Java, C++, and/or other programming languages. Similarly, schematic elements used to represent data or information may be implemented using any suitable electronic arrangement or structure, such as a register, data store, table, record, array, index, hash, map, tree, list, graph, file (of any file type), folder, directory, database, and/or others.

Further, in the drawings, where connecting elements, such as solid or dashed lines or arrows, are used to illustrate a connection, relationship or association between or among two or more other schematic elements, the absence of any such connecting elements is not meant to imply that no connection, relationship or association can exist. In other words, some connections, relationships or associations between elements may not be shown in the drawings so as not to obscure the disclosure. In addition, for ease of illustration, a single connecting element may be used to represent multiple connections, relationships or associations between elements. For example, where a connecting element represents a communication of signals, data or instructions, it should be understood by those skilled in the art that such element may represent one or multiple signal paths (e.g., a bus), as may be needed, to effect the communication.

Referring now to FIG. 1, a system 100 for sharing digital media content includes a media source device 102, a media sink device 104, and a network 106. In operation, the media source device 102 may share digital media content with the media sink device 104 over the network 106 using a security protocol. In the illustrative embodiment, a Digital Transmission Content Protection (DTCP) security protocol is used, such as the Digital Transmission Content Protection over Internet Protocol (DTCP-IP). However, other security protocols may be used in other embodiments.

The media source device 102 initially authenticates the media sink device 104. If the media sink device 104 is successfully authenticated, the media source device 102 and sink device 104 perform a key exchange to generate a shared secret key. The media source device 102 generates a packet encryption key based on the shared key and encrypts the media content using the packet encryption key. The media sink device 104 may decrypt the media content using a shared exchange key. To ensure the security and protection of the media content, the keys and other cryptographic functions generated by the media source device 102 are done so within a security engine 110 of a system-on-a chip (SOC) 112 of the media source device 102. The media source device 102 maintains the keys in secrecy within a secure memory 114 of the security engine 110. In this way, digital media content may be shared with the media sink device 104 while ensuring the security of the digital media content and the encryption keys used to facilitate such secured sharing.

The media source device 102 may be embodied as any type of device capable of delivering digital media content to the media sink device 104. For example, the media source device 102 may be embodied as a set-top box, a digital television, a smartphone, a tablet computer, a laptop computer, a mobile internet device (MID), a desktop computer, or other device capable of delivery of media content. The media source device 102 may be configured to deliver any type of digital media content to the media sink device 104 including, for example, movies, pictures, images, songs, audio and/or video recordings, and/or any other type of audio, video, and/or audio and video content.

As discussed above, the media source device 102 includes the SOC 112, which may be embodied as any type of system-on-a-chip device having various components and structures. In the illustrative embodiment of FIG. 1, the SOC 112 includes the security engine 110, a memory controller 116, a processor core 118, and bus a plurality of hardware peripherals 130, which are communicatively coupled to each other a link 120. The link 120 may be embodied as any type of interconnect such as a bus, point-to-point, or other interconnect capable of facilitating communication between the various components of the SOC 122. The hardware peripherals 130 may include any type of hardware peripheral component depending upon the intended functionality of the SOC 112. For example, in the illustrative embodiment, the hardware peripherals 130 include a demux 132 to separate audio and video content streams, video processing component(s) 134 to process video content, and audio processing component(s) 136 to process audio content. Of course, it should be appreciated that the hardware peripherals 130 of the SOC 112 have been simplified in the illustrative embodiment of FIG. 1 and that the SOC 112 may include additional, different, and/or greater detailed hardware peripherals 130, which are not illustrated in FIG. 1 for clarity of the disclosure.

The security engine 110 may be embodied as a security co-processor or processing circuitry separate from the processor core 118. The security engine 110 includes a security key 150 and the secure memory 114, which is accessible only by the security engine 110. The security engine 110 stores the security key 150, and other cryptographic keys as discussed below, in the secure memory 114. In the illustrative embodiment, the security key 150 is provisioned during the manufacturing of the SOC 112, but may be generated by the SOC 112 during operation in other embodiments. For example, in some embodiments, the security key 150 is based on blown fuses within the security engine 110 itself. Additionally or alternatively, the security engine 110 may include a key-generating module, such as a trusted platform module (TPM), to generate the security key 150. During use, the security engine 110 may use any number of security keys 150, which may be identical or different from each other.

In some embodiments, the media source device 102 may include additional components and structures other than the SOC 112 depending on the type and intended use of the media source device 102. For example, in the illustrative embodiment of FIG. 1, the media source device 102 includes a system memory 160, a data storage 162, a communications output 164, and one or more input/output devices 166. The system memory 160 may be embodied as any type of main memory or data storage locations including, for example, dynamic random access memory devices (DRAM), synchronous dynamic random access memory devices (SDRAM), double-data rate synchronous dynamic random access memory device (DDR SDRAM), mask read-only memory (ROM) devices, erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) devices, flash memory devices, and/or other volatile and/or non-volatile memory devices.

The data storage 162 may be embodied as any type of device or devices configured for the short-term or long-term storage of data such as, for example, memory devices and circuits, memory cards, hard disk drives, solid-state drives, or other data storage devices. In the illustrative embodiment of FIG. 1, encrypted media content 170 may be stored in the data storage 162, which may be subsequently shared with the media sink device 104 as discussed below.

The communications output 164 may be embodied as a simplified output or as various circuits and/or devices to facilitate, for example, communications with the media sink device 104. For example, the communications output 164 (and/or communication circuitry within the SOC 112) may any suitable communication protocol such as Ethernet (i.e. the IEEE 802.3 standard) or Wi-Fi® (i.e., the IEEE 802.11 standard), and/or other communication protocols or standards.

The input/output devices 166 may be embodied as any type of I/O device for interacting with the media source device 102. For example, the I/O devices 166 may include output devices such as a display for displaying media on the media source device 102 and speakers for playing audio content, and/or input devices such as a remote control receiver, a keyboard, a mouse, and/or the like.

The media sink device 104 may be embodied as any type of media device capable of communicating with and receiving media content from the media source device 102. For example, the media sink device 104 may be embodied as a digital television, a smartphone, a tablet computer, a laptop computer, a mobile internet device (MID), a desktop computer, or other electronic device capable of receiving of media content from the media source device 102.

The illustrative media sink device 104 includes a processor 180, a memory 182, communication circuitry 184, and one or more output devices 186, which may be similar to such components found in other media devices. For example, the processor 180 may be embodied as any type of processor capable of executing software/firmware, such as a microprocessor, digital signal processor, microcontroller, or the like, and may include one or more processing cores. The memory 182 may be embodied as any type of memory or data storage locations including, for example, dynamic random access memory devices (DRAM), synchronous dynamic random access memory devices (SDRAM), double-data rate synchronous dynamic random access memory device (DDR SDRAM), mask read-only memory (ROM) devices, erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) devices, flash memory devices, and/or other volatile and/or non-volatile memory devices. The communication circuitry

The communication circuitry 184 may be embodied any type of circuitry and/or device to facilitate, for example, communications with the media source device 102. For example, the communication circuitry 184 may support communication protocols such as Ethernet (i.e. the IEEE 802.3 standard) or Wi-Fi® (i.e., the IEEE 802.11 standard), and/or other communication protocols or standards. The output devices 186 may be embodied as any type of output device for playing, rendering, or otherwise delivering the media content to a user. For example, the output devices 186 may include a display for displaying media on the media sink device 104 and speakers for playing audio content.

The network 106 may be embodied as any number of various wired and/or wireless networks, in the illustrative embodiment, the network 106 is a local area network (LAN) such as a home network, but may be embodied as or otherwise include other networks in other embodiments. For example, in some embodiments, the network 106 may be embodied as an ad-hoc or point-to-point network or a wide area network (WAN). As discussed in more detail below, the media source device 102 is configured to share media content with the media sink device 104 over the network 106.

Referring now to FIG. 2, in use, the security engine 110 of the SOC 112 of the media source device 102 may be provisioned with key material for facilitating the delivery of media content to various sink devices. To do so, the media source device 102 may execute a method 200 for provisioning the security engine 110. The method 200 begins with block 202 in which the security engine 110 receives a source device certificate, a private device key, and a public certification key. The source device certificate, the private device key, and the public certification key are typically generated by a certification authority organization, which acts as a third-party verifier of the authentication of the particular device. The source device certificate includes a unique device identifier or number assigned to the media source device 102 by the certification authority organization to verify the media source device 102 to other media devices. The unique device identifier may also be used to revoke the authorization of the media source device 102 via distribution of a System Renewability Message (SRM) revocation list. The private device key may be used by the media source device 102 to sign the packets so as to authenticate the media source device 102 to other media devices as discussed in more detail below. Conversely, the public certification key may be used by the media sink device 104 to verify the packets received form the media source device 102 during authentication.

In block 204, the security engine 110 stores the source device certificate and the public certification key in the secure memory 114. In some embodiments, the security engine 110 may encrypt the source device certificate and/or the public certification key using the security key 150 stored in the security engine 110. In such embodiments, the security engine 110 may store the encrypted source device certificate and/or the encrypted public certification key in the secure memory 114, in the memory 160, or in the data storage 162.

In block 206, the security engine 110 encrypts the private device key using the security key 150 stored in the security engine 110. In some embodiments, the security engine 110 may also secure the encrypted private device key in block 208. To do so, for example, the security engine may perform a Cipher Block Chaining Message Authentication Code (CBC MAC) on the encrypted private device key. Alternatively, the security engine 110 may use some other cryptographic methodology to secure the encrypted private device key. Regardless, in block 210, the security engine 110 stores the secured, encrypted private device key in the secure memory 114. In this way, the security engine 110 of the SOC 112 of the media source device 102 is provisioned with initial key material to facilitate delivering media to sink devices in a secure manner.

Referring now to FIG. 3, the media source device 102 may use a Digital Transmission Content Protection (DTCP) protocol to share media content with the sink device 104 as discussed above. Prior to the actual sharing of media content with the media sink device 104, the media source device 102 is configured to authenticate the media sink device 104 and negotiate cryptographic keys with the media sink device 104 to facilitate the delivery of media content thereto. To do so, the media source device 102 may execute a method 300 for authenticating the media sink device 104. The method 300 begins with block 302 in which the media source device 102 determines whether a request for authorization has been received from the media sink device 104. If so, in block 304, the media source device 102 receives the sink device certificate and sink public cryptographic key. Similar to the source device certificate of the media source device 102, the sink device certificate is issued by the certification authority organization to verify the media sink device 104. The sink device certificate includes a unique device identifier assigned by the certification authority organization, which uniquely identifies the media sink device 104 from other media devices. The sink public key may be used by the security engine 110 in subsequent communications to verify that received messages were originated by the media sink device 104.

In block 306, the media source device 102 verifies the sink device certificate using the public certification key. In embodiments in which the public certification key is stored in an encrypted form, the security engine 110 of the SOC 112 of the media source device 102 retrieves the encrypted public certification key and decrypts the key using the security key 150. The public certification key is used to verify that the sink device certificate has been properly signed by an authorized media device. As such, in block 308, the media source device 102 determines whether the media sink device 104 is properly certified using the public certification key. If not, the method 300 advances to block 310 in which the media source device 102 rejects the authorization request from the media sink device 104.

However, if the sink device certificate is verified in block 308, the media source device 102 further verifies that the certification of the media sink device 104 has not been revoked. To do so, the media source device 102 may utilize an SRM list, which includes identifiers of devices whose certification has been previously revoked. The SRM list of the media source device 102 may be stored in the secure memory 114 of the SOC 112 in some embodiments. Alternately, the SRM list may be stored in the memory 160 or the data storage 162 in an encrypted or unencrypted form. As new devices are added to the local network of media devices, the SRM list is updated on each device. As such, in block 312, the media source device 102 compares the unique device identifier of the media sink device 104, which was received with the sink device certification, against the current SRM list. If, in block 314, the certification of the media sink device 104 is determined to have been revoked, the method 300 advances to block 310 in which the media source device 102 rejects the authorization request from the media sink device 104.

If, however, the certification of the media sink device is not revoked, the method 300 advances to block 316 in which the security engine 110 of the SOC 112 stores the sink public key in the secure memory 114 of the security engine 110. In block 318, the security engine 110 attic SOC 112 retrieves the source device certificate and private source key from the secure memory 114. Additionally, in block 318, the media source device 102 may retrieve a source public key and a source certificate and send the key and certificate to the media sink device 104. The source public key may be used by the media sink device 104 in subsequent communications to verify that received messages were originated by the media source device 102.

If the media source device is not verified in block 320, the method 300 advances to block 310 in which the media source device 102 rejects the authorization request from the media sink device 104. Alternatively, in some embodiments, the media source device 102 may attempt to resend the source certificate and source public key to the media sink device 104.

However, if the source certificate is verified in block 320, the method 300 advances to block 322 (see FIG. 3B) in which the media source device 102 and the media sink device 104 perform a key exchange. The key exchange is used to establish a shared secret key in the media source device 102 and the media sink device 104 without prior provisioning of the devices 102, 104 with corresponding keys. The media source device 102 may use any appropriate key exchange algorithm to effect the establishment of a shared secret.

In the illustrative embodiment, the media source device 102 uses an elliptic curve Diffie-Hellman (ECDH) key exchange in block 322. To do so, the media source device 102 provisions the media sink device 104 for the Diffie-Hellman key exchange in block 324. For example, media source device 102 may select the elliptic curve, F, and the base point, G, to be used in generating the shared secret. The domain parameters associated with the elliptic curve and base point selections are sent to the media sink device 104 in block 324. Of course, in other embodiments, other Diffie-Hellman key exchanges may be used such as, for example, Rivest-Shamir-Adleman (RSA) Diffie-Hellman key exchange. In such embodiments, the media source device 102 generates the domain parameters (e.g., selects a prime number and a primitive root) and transmits the domain parameters t the media sink device 104 in block 324.

The security engine 110 of the SOC 112 of the media source device 102 may sign the transmission of block 324, and other subsequent transmissions, with the private source key corresponding to the public source key provided to the media sink device 104 in block 318. In some embodiments, the private source key may be the security key 150 or other key stored in the secure memory 114 of the security engine 110.

In block 326, the security engine 110 of the SOC 112 generates a source Diffie-Hellman public and private key based on the domain parameters generated or otherwise determined in block 324. The media source device 102 sends the public Diffie-Hellman key to the media sink device 104 in block 326. Again, such transmission may be signed by the security engine using the private source key (e.g., security key 150).

In block 328, the media source device 102 receives the sink Diffie-Hellman public key from the media sink device 104, which may be calculated in a similar manner as described above in regard to the media source device 102. The media source device 102 stores the sink Diffie-Hellman public key in the secure memory 114 of the security engine 110. Additionally, in block 328, the media source device 102 verifies the signature of the sink Diffie-Hellman public key message, and other subsequent messages received from the media sink device 104, using the sink public key stored in the secure memory 114. If the media source device 102 determines that the message, or other message, is not properly signed, the method 300 advances to block 310 in which the media source device 102 rejects the authorization request from the media sink device 104.

In block 332, the security engine 110 of the SOC 112 of generates an authentication key, K_(AUTH), using the source Diffie-Hellman private key and the sink Diffie-Hellman public key. The security engine 110 may store the authentication key, K_(AUTH), the secure memory 114. In the illustrative embodiment, for example, the security engine 110 performs an elliptic curve scalar multiplication using the source Diffie-Hellman private key and the sink Diffie-Hellman public to generate the authentication key, K_(AUTH). Of course, other cryptographic calculations may be performed in block 332 in other embodiments to generate the authentication key, K_(AUTH). However, any such calculations occur in the security engine 110 to maintain the security of the authentication process.

In block 334, the security engine 110 generates an exchange key, K_(X), In the illustrative embodiments, the exchange key, K_(X), is embodied as a random nonce, but may be generated using other methodologies or calculations in other embodiments. The nonce is a random or pseudo-random number intended to be used only once in cryptographic functions to thwart, for example, replay attacked.

In block 336, the security engine 110 of the SOC 112 scrambles the exchange key, K_(X), using the authentication key, K_(AUTH). The security engine 110 may use any suitable cryptographic calculation or scrambling algorithm/methodology to scramble the exchange key, K_(X). Subsequently, in block 338, the media source device 102 sends the scrambled exchange key to the media sink device 104. Again, as discussed above, such message may be signed by the security engine 110 of the SOC 112 using the private device key (e.g., the security key 150). The media sink device 104 may generate the exchange key, K_(X), using the shared authentication key, K_(AUTH). In this way, a shared secret key is established between the media source device 102 and the media sink device 104 using the security engine 110 of the SOC 112 of the media source device 102.

After the media source device 102 and the media sink device 104 have established the shared secret key via the method 300, the media source device 102 may share media content with the media sink device 104 using the shared secret key. To do so, the media source device 102 may execute a method 400 for sharing media content with the media sink device 104. The method 400 begins with block 402 in which the media source device 102 obtains media content to be shared with the media sink device 104. Such media content may be stored in the media source device 102 as encrypted media content 170 or may be received by the media source device 102 from an external source (e.g., streamed or transmitted to the media source device 102 such as digital cable TV).

In block 404, the security engine 110 of the media source device 102 generates a random nonce, which is used to combat replay attacks. In block 406, the security engine 110 generates a packet encryption key, K_(C), using the exchange key, K_(X), the random nonce generated in block 404, and an encryption mode indicator (EMI), which is used for copy control of media content, in the illustrative embodiment, the security engine 110 utilizes an Advanced Encryption Standard-Cipher Block Chaining (AES-CBC) algorithm to generate the packet encryption key, K_(X). However, other encryption algorithms may be used in other embodiments. It should be appreciated that a new packet encryption key, K_(C), is generated in the security engine for each packet of media content sent to the media sink device 104.

In block 408, the security engine 110 encrypts the media content, or a portion thereof, to be sent to the media sink device 104 using the packet encryption key, K_(C). Of course, if the media content is stored on the media source device 102 in an encrypted format (which would be encrypted using an encryption key other than the packet encryption key, K_(C)), the media source device 102 decrypts the media content before re-encrypting the media content with the packet encryption key, K_(C).

In block 410, the media source device 102 encapsulates the encrypted media content, the random nonce generated in block 404, and the EMI into a Protected Content Packet (PCP) packet. Of course, other encapsulation methodologies may be used in other embodiments. Subsequently, in block 412, the media source device 102 sends the encapsulated packet to the media sink device 104. It should be appreciated that the media source device 102 may send multiple packets to the media sink device 104 to effect the secure delivery of the media content to the media sink device 104. The media sink device 104 may decrypt the media content using the exchange key, K_(X), as discussed above.

While the disclosure has been illustrated and described in detail in the drawings and foregoing description, such an illustration and description is to be considered as exemplary and not restrictive in character, it being understood that only illustrative embodiments have been shown and described and that all changes and modifications consistent with the disclosure and recited claims are desired to be protected. 

1-39. (canceled)
 40. A system-on-a-chip apparatus comprising: a system-on-a-chip comprising a security engine having a secure memory accessible only by the security engine, the security engine to: perform a cryptographic key exchange with a sink device; generate an authorization key as a function of the cryptographic key exchange; and generate an exchange key using the authorization key; store the authorization key and the exchange key in the secure memory; and encrypt media content as a function of the exchange key to share the encrypted media content with the sink device using a Digital Transmission Content Protection security protocol.
 41. The system-on-a-chip apparatus of claim 40, wherein the security engine to perform a Diffie-Hellman cryptographic key exchange with the sink device to generate the authorization key.
 42. The system-on-a-chip apparatus of claim 41, wherein the Diffie-Hellman cryptographic key exchange is an elliptic curve Diffie-Hellman cryptographic key exchange.
 43. The system-on-a-chip apparatus of claim 42, wherein the security engine to: generate a source Diffie-Hellman public key and a source Diffie-Hellman private key; receive a sink Diffie-Hellman public key from the sink device; and perform an elliptic curve scalar multiplication as a function of the source Diffie-Hellman private key and the sink Diffie-Hellman public key.
 44. The system-on-a-chip apparatus of claim 40, wherein the security engine to generate a first exchange key and generate a scrambled exchange key using the first exchange key and the authorization key.
 45. The system-on-a-chip apparatus of claim 40, wherein the security engine to obtain media content to share with the sink device, generate a packet encryption key as a function of the exchange key, and encrypt the content media using the packet encryption key.
 46. The system-on-a-chip apparatus of claim 45, wherein the security engine to: generate a random number in the security engine and generate the packet encryption key as a function of the exchange key and the random number; and encapsulate the encrypted content media, the random number, and an encryption mode indicator.
 47. The system-on-a-chip apparatus of claim 40, wherein the security engine to receive a certificate from the sink device, retrieve a public certification key from the secure memory, and verify the certificate received from the sink device using the public certification key.
 48. The system-on-a-chip apparatus of claim 47, wherein the security engine to receive a sink public key from the sink device and store the sink public key in the secured memory, the sink public key to authenticate communications received from the sink device.
 49. One or more machine-readable storage media comprising a plurality of instructions stored thereon that, in response to execution by a computing device, cause the computing device to: perform a cryptographic key exchange with a sink device; generate an authorization key in a security engine of a system-on-a-chip of the computing device as a function of the cryptographic key exchange; store the authorization key in a secure memory of the security engine of the system-on-a-chip; generate an exchange key in the security engine of the system-on-a-chip based on the authorization key; store the exchange key in the secure memory of the security engine of the system-on-a-chip, the exchange key to encrypt media content for sharing with the sink device.
 50. The one or more machine-readable storage media of claim 49, wherein to perform a cryptographic key exchange comprises to perform a Diffie-Hellman cryptographic key exchange with the sink device.
 51. The one or more machine-readable storage media of claim 50, wherein to perform the Diffie-Hellman cryptographic key exchange comprises to perform an elliptic curve Diffie-Hellman cryptographic key exchange.
 52. The one or more machine-readable storage media of claim 51, wherein to perform the Diffie-Hellman cryptographic key exchange comprises to (i) generate a source Diffie-Hellman public key and a source Diffie-Hellman private key in the security engine of the system-on-a-chip and (ii) receive a sink Diffie-Hellman public key from the sink device; and wherein to generate the authorization key comprises to perform an elliptic curve scalar multiplication in the security engine of the system-on-a-chip as a function of the source Diffie-Hellman private key and the sink Diffie-Hellman public key.
 53. The one or more machine-readable storage media of claim 49, wherein to generate the exchange key in the security engine comprises to: generate a first exchange key in the security engine, and generate a scrambled exchange key in the security engine of the system-on-a-chip based on the first exchange key and the authorization key.
 54. The one or more machine-readable storage media of claim 53, wherein to generate an exchange key comprises to generate a random number in the security engine of the system-on-a-chip.
 55. The one or more machine-readable storage media of claim 49, wherein the plurality of instructions further cause the computing device to: obtain content media to share with the sink device; generate a packet encryption key in the security engine of the system-on-a-chip as a function of the exchange key; and encrypt the content media based on the packet encryption key.
 56. The one or more machine-readable storage media of claim 55, wherein to generate a packet encryption key comprises to: generate a random number in the security engine; and generate a packet encryption key as a function of the exchange key and the random number; and wherein the plurality of instructions further cause the computing device to: encapsulate the encrypted content media, the random number, and an encryption mode indicator in the security engine of the system-on-a-chip; and transmit the encapsulated packet to the sink device.
 57. The one or more machine-readable storage media of claim 49, wherein the plurality of instructions further cause the computing device to: receive a certificate from the sink device; retrieve a public certification key from a secure memory of the security engine of the system-on-a-chip; and verify the certificate received from the sink device using the public certification key.
 58. The one or more machine-readable storage media of claim 57, wherein the plurality of instructions further cause the computing device to: receive a sink public key from the sink device; and store the sink public key in the secured memory of the security engine of the system-on-a-chip, the sink public key to authenticate communications received from the sink device.
 59. The one or more machine-readable storage media of claim 49, wherein the plurality of instructions further cause the computing device to: receive a public certification key with the security engine of the system-on-a-chip; and store the public certification key in secure memory of the security engine, the public certification key to verify certificates received from the sink device.
 60. The one or more machine-readable storage media of claim 49, wherein the plurality of instructions further cause the computing device to: generate a security key in the security engine of the system-on-a-chip; and store the security key in the secured memory of the security engine.
 61. The one or more machine-readable storage media of claim 60, wherein the plurality of instructions further cause the computing device to: receive a source private device key with the security engine of the system-on-a-chip; encrypt the source private device key using the security key; store the encrypted source private device key in the secure memory of the security engine of the system-on-a-chip; and generate a source certificate in the security engine of the system-on-a-chip using the source private device key.
 62. One or more machine-readable storage media comprising a plurality of instructions stored thereon that, in response to execution by a computing device, cause the computing device to: generate a source Diffie-Hellman private key in a security engine of a system-on-a-chip of a source device; receive a sink Diffie-Hellman public key from a sink device; generate an authorization key in the security engine of the system-on-a-chip as a function of the source Diffie-Hellman private key and the sink Diffie-Hellman public key; generate an exchange key in the security engine of the system-on-a-chip; generate a scrambled exchange key in the security engine of the system-on-a-chip using the exchange key and the authorization key; generate a random number in the security engine of the system-on-a-chip; generate a packet encryption key in the security engine of the system-on-a-chip as a function of the exchange key and the random number; and encrypt media content using the packet encryption key.
 63. The one or more machine-readable storage media of claim 62, wherein to generate the authorization key comprises to perform an elliptic curve scalar multiplication in the security engine of the system-on-a-chip as a function of the source Diffie-Hellman private key and the sink Diffie-Hellman public key.
 64. The one or more machine-readable storage media of claim 62, wherein to generate an exchange key comprises to generate a random number in the security engine of the system-on-a-chip; and wherein the plurality of instructions further cause the computing device to: encapsulate the encrypted content media, the random number, and an encryption mode indicator in the security engine of the system-on-a-chip; and transmit the encapsulated packet to the sink device. 